The system's access control program must log each system access attempt.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-227956	GEN006600	SV-227956r603266_rule		Medium

Description
If access attempts are not logged, then multiple attempts to log on to the system by an unauthorized user may go undetected.

STIG	Date
Solaris 10 X86 Security Technical Implementation Guide	2020-12-04

Details

Check Text ( C-36483r603052_chk )
Normally, TCPD logs to the mail facility in /etc/syslog.conf. Determine if syslog is configured to log events by TCPD. Procedure: # more /etc/syslog.conf Look for entries similar to the following: mail.debug /var/adm/maillog mail.none /var/adm/maillog mail.* /var/log/mail auth.info /var/log/messages The above entries would indicate mail alerts are being logged. If no entries for mail exist, then TCPD is not logging and this is a finding.

Check Text ( C-36483r603052_chk )

Normally, TCPD logs to the mail facility in /etc/syslog.conf. Determine if syslog is configured to log events by TCPD.

Procedure:
# more /etc/syslog.conf

Look for entries similar to the following:
mail.debug /var/adm/maillog
mail.none /var/adm/maillog
mail.* /var/log/mail
auth.info /var/log/messages

The above entries would indicate mail alerts are being logged. If no entries for mail exist, then TCPD is not logging and this is a finding.

Fix Text (F-36447r603053_fix)
Configure the access restriction program to log every access attempt. Ensure the implementation instructions for TCP_WRAPPERS are followed, so system access attempts are logged into the system log files. If an alternate application is used, it must support this function.